gh-156780: Emscripten: add missing EM_JS_DEPS - #156798

@hoodmane first PR that add the EM_JS_DEPS() everywhere

Noting that CI is currently failing because of a duplicated symbol; that seems to suggest there's a need to collate these declarations into a single coherent location so that we can avoid duplication, rather than co-locating them with usage.

Also - can I ask that you please don't force push. We don't care about a "messy" commit history; CPython uses merge commits, so any messy history isn't preserved after merge. Force pushes also mean that we can lose the context for review comments, and it's really easy to force push a merge comment that pings the entire core team for comment.

Emscripten's normal style guide is to put these next to the symbol that uses them so I think that's alright. I think we have a conflict with #156335, need to merge a main that includes that commit and fix the duplicate symbol.

@freakboy3742 "Noting that CI is currently failing because of a duplicated symbol" ?

The build fail no?
Something like

dup.c >>>
EM_JS_DEPS(tag_a, "$FS");

EM_JS_DEPS(tag_a, "$PATH");  

dup.c:3:1: error: redefinition of '__em_lib_deps_tag_a'
dup.c:1:1: note: previous definition is here

The issue here is that my fork was not up to date with main.

Also about the force push well noted, I had to do it here to properly rebase on latest master